Compare Page

Objectivity

Characteristic Name: Objectivity
Dimension: Reliability and Credibility
Description: Data are unbiased and impartial
Granularity: Information object
Implementation Type: Process-based approach
Characteristic Type: Usage

Verification Metric:

The number of tasks failed or under performed due to biased and partial data
The number of complaints received due to biased or partial data

GuidelinesExamplesDefinitons

The implementation guidelines are guidelines to follow in regard to the characteristic. The scenarios are examples of the implementation

Guidelines: Scenario:
Identify all the factors that make a particular data/information biased for the intended use and take preventive actions to eliminate them (1) A written questionnaire is better than a face to face interviews in getting sensitive personal data
Design and execute preventive actions for all possible information distortions (malfunctioning or personal biases) which may cause by information /data collectors Perform a duel coder approach to code qualitative data.
Design and execute preventive actions for all possible information distortions (malfunctioning or personal biases) which may cause by information /data transmitters (1) After a survey is performed, each participant is contacted individually by a party (other than the person who conducted the survey) and randomly verify if the participants real responses have been marked properly.

Validation Metric:

How mature is the process to prevent biased and partial data

These are examples of how the characteristic might occur in a database.

Example: Source:
Consider an inventory database that contains part numbers, warehouse locations, quantity on hand, and other information. However, it does not contain source information (where the parts came from). If a part is supplied by multiple suppliers, once the parts are received and put on the shelf there is no indication of which supplier the parts came from. The information in the database is always accurate and current. For normal inventory transactions and deci- sion making, the database is certainly of high quality. If a supplier reports that one of their shipments contained defective parts, this database is of no help in identifying whether they have any of those parts or not. The database is of poor quality because it does not contain a relevant element of information. Without that information, the database is poor data quality for the intended use. J. E. Olson, “Data Quality: The Accuracy Dimension”, Morgan Kaufmann Publishers, 9 January 2003.

The Definitions are examples of the characteristic that appear in the sources provided.

Definition: Source:
The degree to which Information is presented without bias, enabling the Knowledge Worker to understand the meaning and significance without misinterpretation. ENGLISH, L. P. 2009. Information quality applied: Best practices for improving business information, processes and systems, Wiley Publishing.
Is the information free of distortion, bias, or error? EPPLER, M. J. 2006. Managing information quality: increasing the value of information in knowledge-intensive products and processes, Springer.
1) Data are unbiased and impartial

2) Objectivity is the extent to which data are unbiased (unprejudiced) and impartial.

WANG, R. Y. & STRONG, D. M. 1996. Beyond accuracy: What data quality means to data consumers. Journal of management information systems, 5-33.

 

Information value

Characteristic Name: Information value
Dimension: Usability and Interpretability
Description: Quality information should provide a business value to the organization
Granularity: Information object
Implementation Type: Process-based approach
Characteristic Type: Usage

Verification Metric:

The number of tasks failed or under performed due to the lack of business value delivered by the information
The number of complaints received due to the lack of business value delivered by the information

GuidelinesExamplesDefinitons

The implementation guidelines are guidelines to follow in regard to the characteristic. The scenarios are examples of the implementation

Guidelines: Scenario:
Continuously asses the relevance and the usefulness of existing data to the organisational goals (Strategic level). (1)What is the cost of poor quality customer data to the organisation in concern?
(2) What revenue can be generated from data?
Continuously asses the usefulness of information based on the tasks at hand (Operational level) (1) Can we predict our future market share from the existing market information?
Monitor and Measure if the intended goal of the data presentation/Interpretation is achieved (1) Employee efficiency data is displayed in a dash board to motivate employees. The effectiveness of this display can be measured by examining the efficiency gain of each employee.
(2) Has the given sales forecast for the last three years been reasonably accurate compared to actuals.

Validation Metric:

How mature is the process to maintain the business value of information

These are examples of how the characteristic might occur in a database.

Example: Source:
Consider a database containing orders from customers. A practice for handling complaints and returns is to create an “adjustment” order for backing out the original order and then writing a new order for the corrected information if applicable. This procedure assigns new order numbers to the adjustment and replacement orders. For the accounting department, this is a high-quality database. All of the numbers come out in the wash. For a business analyst trying to determine trends in growth of orders by region, this is a poor-quality database. If the business analyst assumes that each order number represents a distinct order, his analysis will be all wrong. Someone needs to explain the practice and the methods necessary to unravel the data to get to the real numbers (if that is even possible after the fact). J. E. Olson, “Data Quality: The Accuracy Dimension”, Morgan Kaufmann Publishers, 9 January 2003.

The Definitions are examples of the characteristic that appear in the sources provided.

Definition: Source:
1) A measure of the degree to which data will produce the desired business transaction or outcome.

2) A measure of the perception of and confidence in the quality of the data; the importance, value, and relevance of the data to business needs.

D. McGilvray, “Executing Data Quality Projects: Ten Steps to Quality Data and Trusted Information”, Morgan Kaufmann Publishers, 2008.
As a data quality-oriented organization matures, the agreement of usage will move from a small set of “early adopters” to gradually encompass more and more of the enterprise, Ubiquity measures the degree to which different departments in an organization use shared reference data. LOSHIN, D. 2001. Enterprise knowledge management: The data quality approach, Morgan Kaufmann Pub.
Data are beneficial and provide advantages for their use. WANG, R. Y. & STRONG, D. M. 1996. Beyond accuracy: What data quality means to data consumers. Journal of management information systems, 5-33.